Although the Selerix data transmittal XML can be created in any development environment that has the ability to produce well-formed XML, we highly recommend using our .NET library for this purpose. The library encapsulates the Selerix Data Model in a familiar object paradigm that lets developers focus on the data being transferred instead of the data container. In addition to exposing all members of the data transmittal, environments that support Intelligent code completion (ICC) technologies such as Visual Studio's Intellisense can significantly reduce development time by preventing mistakes that can be difficult to diagnose in a RPC environment.
Many of the transmittal XML samples included in this documentation were generated with the SerializeToString method of the SerializationHelper class in the Selerix .NET library.
Developers who use Visual Studio or a similar development environment which provides intelligent code completion helpers are at a significant advantage over those who build the Selerix data transmittal XML manually. The image below shows how Visual Studio's Intellisense exposes the Selerix Data Model in the form of a transmittal object, making the process of building a Selerix data transmittal much easier and less prone to mistakes:
Even when the production environment precludes use of the Selerix .NET library directly, the helpers can be used as a reference for building valid transmittal XML. From Visual Studio or a similarly capable development environment:
Developers who want to take advantage of the Selerix .NET Library but who do not have access to an ICC-enabled development environment may use the BenSelect report editor online to create a custom data transmittal XML for use as a reference.
The JScript.NET source example in the BenSelect report editor topic in this section shows how to instantiate a Transmittal object, set the appropriate properties, and serialize the data using the Selerix .NET Library from within the BenSelect report editor. Although the example creates a transmittal for use in a BenSelect enrollment integration, the steps are the same regardless of the purpose of the transmittal.
Note that the Event object referenced in the sample source is specific to BenSelect reporting and should be omitted in source that is used outside of the report editor.